Transport behavior observation

ABSTRACT

An example operation includes one or more of receiving indications from a plurality of transports, by a server, of another transport in proximity to the plurality of transports, forming a consensus, by the server, from the indications from the plurality of transports, and transmitting, by the server, a notification to one or more of the other transport and a device associated with the other transport, in response to the consensus. Each indication includes an identifier of the other transport and an identification of one or more ways the other transport is being operated in a different manner than intended.

TECHNICAL FIELD

This application generally relates to correcting non-optimal operationof a transport, and more particularly, to transport behaviorobservation.

BACKGROUND

Vehicles or transports, such as cars, motorcycles, trucks, planes,trains, etc., generally provide transportation needs to occupants and/orgoods in a variety of ways. Functions related to transports may beidentified and utilized by various computing devices, such as asmartphone or a computer.

Transports already include cameras and sensors for accident avoidanceand parking assistance. They provide images to drivers to assist inmaneuvering a transport or not maneuvering a transport to avoidpotential accidents. Although such cameras and sensors are primary usedfor improvements related to the same transport, in some cases suchcameras and sensors may be used to improve operation of othertransports.

SUMMARY

One example embodiment provides a method that includes one or more ofreceiving, by a memory on a transport, a first portion of a softwareupdate from a server, and in response to at least one device associatedwith the transport is proximate to the transport, receiving, by thememory, a second portion from the at least one device, performing, by aprocessor on the transport, the software update, and providing, by thetransport, a notification of a completion of the software update to theat least one device.

Another example embodiment provides a transport that includes aprocessor and a memory, coupled to the processor. The memory includesinstructions that when executed by the processor are configured toperform one or more of receive, by the memory, a first portion of asoftware update from a server. In response to at least one deviceassociated with the transport is proximate to the transport, the memoryreceives a second portion from the at least one device, the processorperforms the software update, and the transport provides a notificationof a completion of the software update to the at least one device.

A further example embodiment provides a non-transitory computer readablemedium comprising instructions, that when read by a processor, cause theprocessor to perform one or more of receiving, by a memory on atransport, a first portion of a software update from a server, inresponse to at least one device associated with the transport isproximate to the transport, receiving, by the memory, a second portionfrom the at least one device, performing, by a processor on thetransport, the software update, and providing, by the transport, anotification of a completion of the software update to the at least onedevice.

One example embodiment provides a method that includes one or more ofdetecting, by a transport, a difference between sensor data associatedwith a location outside the transport and data stored on the transportand updating, by the transport, the data stored on the transport withthe difference.

Another example embodiment provides a transport that includes aprocessor and a memory, coupled to the processor. The memory includesinstructions that when executed by the processor are configured toperform one or more of detect, by the transport, a difference betweensensor data associated with a location outside the transport and datastored on the transport and update, by the transport, the data stored onthe transport with the difference.

A further example embodiment provides a non-transitory computer readablemedium comprising instructions, that when read by a processor, cause theprocessor to perform one or more of detecting, by a transport, adifference between sensor data associated with a location outside thetransport and data stored on the transport and updating, by thetransport, the data stored on the transport with the difference.

One example embodiment provides a method that includes one or more ofreceiving indications from a plurality of transports, by a server, ofanother transport in proximity to the plurality of transports, forming aconsensus, by the server, from the indications from the plurality oftransports, and transmitting, by the server, a notification to one ormore of the other transport and a device associated with the othertransport, in response to the consensus. Each indication includes anidentifier of the other transport and an identification of one or moreways the other transport is being operated in a different manner thanintended.

Another example embodiment provides a transport that includes aprocessor and a memory, coupled to the processor. The memory includesinstructions that when executed by the processor are configured toperform one or more of receive indications from a plurality oftransports of another transport in proximity to the plurality oftransports, form a consensus from the indications from the plurality oftransports, and transmit a notification to one or more of the othertransport and a device associated with the other transport, in responseto the consensus. Each indication includes an identifier of the othertransport and an identification of one or more ways the other transportis being operated in a different manner than intended.

A further example embodiment provides a non-transitory computer readablemedium comprising instructions, that when read by a processor, cause theprocessor to perform one or more of receiving indications from aplurality of transports, by a server, of another transport in proximityto the plurality of transports, forming a consensus, by the server, fromthe indications from the plurality of transports, and transmitting, bythe server, a notification to one or more of the other transport and adevice associated with the other transport. In response to theconsensus, each indication includes an identifier of the other transportand an identification of one or more ways the other transport is beingoperated in a different manner than intended.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example diagram of a transport software update,according to example embodiments.

FIG. 1B illustrates an example diagram of data discrepancy resolutionfor a transport, according to example embodiments.

FIG. 1C illustrates an example diagram of transport behaviorobservation, according to example embodiments.

FIG. 2A illustrates a transport network diagram, according to exampleembodiments.

FIG. 2B illustrates another transport network diagram, according toexample embodiments.

FIG. 2C illustrates yet another transport network diagram, according toexample embodiments.

FIG. 2D illustrates a further transport network diagram, according toexample embodiments.

FIG. 2E illustrates a yet further transport network diagram, accordingto example embodiments.

FIG. 3A illustrates a flow diagram, according to example embodiments.

FIG. 3B illustrates another flow diagram, according to exampleembodiments.

FIG. 3C illustrates yet another flow diagram, according to exampleembodiments.

FIG. 4 illustrates a machine learning transport network diagram,according to example embodiments.

FIG. 5A illustrates an example vehicle configuration for managingdatabase transactions associated with a vehicle, according to exampleembodiments.

FIG. 5B illustrates another example vehicle configuration for managingdatabase transactions conducted among various vehicles, according toexample embodiments

FIG. 6A illustrates a blockchain architecture configuration, accordingto example embodiments.

FIG. 6B illustrates another blockchain configuration, according toexample embodiments.

FIG. 6C illustrates a blockchain configuration for storing blockchaintransaction data, according to example embodiments.

FIG. 6D illustrates example data blocks, according to exampleembodiments.

FIG. 7 illustrates an example system that supports one or more of theexample embodiments.

DETAILED DESCRIPTION

It will be readily understood that the instant components, as generallydescribed and illustrated in the figures herein, may be arranged anddesigned in a wide variety of different configurations. Thus, thefollowing detailed description of the embodiments of at least one of amethod, apparatus, non-transitory computer readable medium and system,as represented in the attached figures, is not intended to limit thescope of the application as claimed but is merely representative ofselected embodiments.

The instant features, structures, or characteristics as describedthroughout this specification may be combined in any suitable manner inone or more embodiments. For example, the usage of the phrases “exampleembodiments”, “some embodiments”, or other similar language, throughoutleast this specification refers to the fact that a particular feature,structure, or characteristic described in connection with the embodimentmay be included in at one embodiment. Thus, appearances of the phrases“example embodiments”, “in some embodiments”, “in other embodiments”, orother similar language, throughout this specification do not necessarilyall refer to the same group of embodiments, and the described features,structures, or characteristics may be combined in any suitable manner inone or more embodiments. In the diagrams, any connection betweenelements can permit one-way and/or two-way communication even if thedepicted connection is a one-way or two-way arrow. In the currentapplication, a transport may include one or more of cars, trucks,motorcycles, scooters, bicycles, boats, recreational vehicles, planes,and any object that may be used to transport people and or goods fromone location to another.

In addition, while the term “message” may have been used in thedescription of embodiments, the application may be applied to many typesof network data, such as, a packet, frame, datagram, etc. The term“message” also includes packet, frame, datagram, and any equivalentsthereof. Furthermore, while certain types of messages and signaling maybe depicted in exemplary embodiments they are not limited to a certaintype of message, and the application is not limited to a certain type ofsignaling.

Example embodiments provide methods, systems, components, non-transitorycomputer readable media, devices, and/or networks, which provide atleast one of: a transport (also referred to as a vehicle herein) a datacollection system, a data monitoring system, a verification system, anauthorization system and a vehicle data distribution system. The vehiclestatus condition data, received in the form of communication updatemessages, such as wireless data network communications and/or wiredcommunication messages, may be received and processed to identifyvehicle/transport status conditions and provide feedback as to thecondition changes of a transport. In one example, a user profile may beapplied to a particular transport/vehicle to authorize a current vehicleevent, service stops at service stations, and to authorize subsequentvehicle rental services.

Within the communication infrastructure, a decentralized database is adistributed storage system, which includes multiple nodes thatcommunicate with each other. A blockchain is an example of adecentralized database which includes an append-only immutable datastructure (i.e. a distributed ledger) capable of maintaining recordsbetween untrusted parties. The untrusted parties are referred to hereinas peers, nodes or peer nodes. Each peer maintains a copy of thedatabase records and no single peer can modify the database recordswithout a consensus being reached among the distributed peers. Forexample, the peers may execute a consensus protocol to validateblockchain storage entries, group the storage entries into blocks, andbuild a hash chain via the blocks. This process forms the ledger byordering the storage entries, as is necessary, for consistency. In apublic or permissionless blockchain, anyone can participate without aspecific identity. Public blockchains can involve cryptocurrencies anduse consensus based on various protocols such as proof of work (PoW). Onthe other hand, a permissioned blockchain database provides a system,which can secure interactions among a group of entities which share acommon goal, but which do not or cannot fully trust one another, such asbusinesses that exchange funds, goods, information, and the like. Theinstant application can function in a permissioned and/or apermissionless blockchain setting.

Smart contracts are trusted distributed applications which leveragetamper-proof properties of the shared or distributed ledger (i.e., whichmay be in the form of a blockchain) database and an underlying agreementbetween member nodes which is referred to as an endorsement orendorsement policy. In general, blockchain entries are “endorsed” beforebeing committed to the blockchain while entries, which are not endorsedare disregarded. A typical endorsement policy allows smart contractexecutable code to specify endorsers for an entry in the form of a setof peer nodes that are necessary for endorsement. When a client sendsthe entry to the peers specified in the endorsement policy, the entry isexecuted to validate the entry. After validation, the entries enter anordering phase in which a consensus protocol is used to produce anordered sequence of endorsed entries grouped into blocks.

Nodes are the communication entities of the blockchain system. A “node”may perform a logical function in the sense that multiple nodes ofdifferent types can run on the same physical server. Nodes are groupedin trust domains and are associated with logical entities that controlthem in various ways. Nodes may include different types, such as aclient or submitting-client node which submits an entry-invocation to anendorser (e.g., peer), and broadcasts entry-proposals to an orderingservice (e.g., ordering node). Another type of node is a peer node whichcan receive client submitted entries, commit the entries and maintain astate and a copy of the ledger of blockchain entries. Peers can alsohave the role of an endorser, although it is not a requirement. Anordering-service-node or orderer is a node running the communicationservice for all nodes, and which implements a delivery guarantee, suchas a broadcast to each of the peer nodes in the system when committingentries and modifying a world state of the blockchain, which is anothername for the initial blockchain entry, which normally includes controland setup information.

A ledger is a sequenced, tamper-resistant record of all statetransitions of a blockchain. State transitions may result from smartcontract executable code invocations (i.e., entries) submitted byparticipating parties (e.g., client nodes, ordering nodes, endorsernodes, peer nodes, etc.). An entry may result in a set of assetkey-value pairs being committed to the ledger as one or more operands,such as creates, updates, deletes, and the like. The ledger includes ablockchain (also referred to as a chain) which is used to store animmutable, sequenced record in blocks. The ledger also includes a statedatabase, which maintains a current state of the blockchain. There istypically one ledger per channel. Each peer node maintains a copy of theledger for each channel of which they are a member.

A chain is an entry log, which is structured as hash-linked blocks, andeach block contains a sequence of N entries where N is equal to orgreater than one. The block header includes a hash of the block'sentries, as well as a hash of the prior block's header. In this way, allentries on the ledger may be sequenced and cryptographically linkedtogether. Accordingly, it is not possible to tamper with the ledger datawithout breaking the hash links. A hash of a most recently addedblockchain block represents every entry on the chain that has comebefore it, making it possible to ensure that all peer nodes are in aconsistent and trusted state. The chain may be stored on a peer nodefile system (i.e., local, attached storage, cloud, etc.), efficientlysupporting the append-only nature of the blockchain workload.

The current state of the immutable ledger represents the latest valuesfor all keys that are included in the chain entry log. Because thecurrent state represents the latest key values known to a channel, it issometimes referred to as a world state. Smart contract executable codeinvocations execute entries against the current state data of theledger. To make these smart contract executable code interactionsefficient, the latest values of the keys may be stored in a statedatabase. The state database may be simply an indexed view into thechain's entry log, it can therefore be regenerated from the chain at anytime. The state database may automatically be recovered (or generated ifneeded) upon peer node startup, and before entries are accepted.

A blockchain is different from a traditional database in that theblockchain is not a central storage but rather a decentralized,immutable, and secure storage, where nodes must share in changes torecords in the storage. Some properties that are inherent in blockchainand which help implement the blockchain include, but are not limited to,an immutable ledger, smart contracts, security, privacy,decentralization, consensus, endorsement, accessibility, and the like.

Example embodiments provide a way for providing a vehicle service to aparticular vehicle and/or requesting user associated with a user profilethat is applied to the vehicle. For example, a user may be the owner ofa vehicle or the operator of a vehicle owned by another party. Thevehicle may require service at certain intervals and the service needsmay require authorization prior to permitting the services to bereceived. Also, service centers may offer services to vehicles in anearby area based on the vehicle's current route plan and a relativelevel of service requirements (e.g., immediate, severe, intermediate,minor, etc.). The vehicle needs may be monitored via one or more sensorswhich report sensed data to a central controller computer device in thevehicle, which in turn, is forwarded to a management server for reviewand action.

A sensor may be located on one or more of the interior of the transport,the exterior of the transport, on a fixed object apart from thetransport, and on another transport near to the transport. The sensormay also be associated with the transport's speed, the transport'sbraking, the transport's acceleration, fuel levels, service needs, thegear-shifting of the transport, the transport's steering, and the like.The notion of a sensor may also be a device, such as a mobile device.Also, sensor information may be used to identify whether the vehicle isoperating safely and whether the occupant user has engaged in anyunexpected vehicle conditions, such as during the vehicle access period.Vehicle information collected before, during and/or after a vehicle'soperation may be identified and stored in a transaction on ashared/distributed ledger, which may be generated and committed to theimmutable ledger as determined by a permission granting consortium, andthus in a “decentralized” manner, such as via a blockchain membershipgroup.

Each interested party (i.e., company, agency, etc.) may want to limitthe exposure of private information, and therefore the blockchain andits immutability can limit the exposure and manage permissions for eachparticular user vehicle profile. A smart contract may be used to providecompensation, quantify a user profile score/rating/review, apply vehicleevent permissions, determine when service is needed, identify acollision and/or degradation event, identify a safety concern event,identify parties to the event and provide distribution to registeredentities seeking access to such vehicle event data. Also, the resultsmay be identified, and the necessary information can be shared among theregistered companies and/or individuals based on a “consensus” approachassociated with the blockchain. Such an approach could not beimplemented on a traditional centralized database.

Every autonomous driving system is built on a whole suite of softwareand an array of sensors. Machine learning, lidar projectors, radar, andultrasonic sensors all work together to create a living map of the worldthat a self-driving car can navigate. Most companies in the race to fullautonomy are relying on the same basic technological foundations oflidar+radar+cameras+ultrasonic, with a few notable exceptions.

In another embodiment, GPS, maps and other cameras and sensors are usedin autonomous vehicles without lidar as lidar is often viewed as beingexpensive and unnecessary. Researchers have determined that stereocameras are a low-cost alternative to the more expensive lidarfunctionality.

The instant application includes, in certain embodiments, authorizing avehicle for service via an automated and quick authentication scheme.For example, driving up to a charging station or fuel pump may beperformed by a vehicle operator and the authorization to receive chargeor fuel may be performed without any delays provided the authorizationis received by the service station. A vehicle may provide acommunication signal that provides an identification of a vehicle thathas a currently active profile linked to an account that is authorizedto accept a service which can be later rectified by compensation.Additional measures may be used to provide further authentication, suchas another identifier may be sent from the user's device wirelessly tothe service center to replace or supplement the first authorizationeffort between the transport and the service center with an additionalauthorization effort.

Data shared and received may be stored in a database, which maintainsdata in one single database (e.g., database server) and generally at oneparticular location. This location is often a central computer, forexample, a desktop central processing unit (CPU), a server CPU, or amainframe computer. Information stored on a centralized database istypically accessible from multiple different points. A centralizeddatabase is easy to manage, maintain, and control, especially forpurposes of security because of its single location. Within acentralized database, data redundancy is minimized as a single storingplace of all data also implies that a given set of data only has oneprimary record.

FIG. 1A illustrates an example diagram of a transport software update100, according to example embodiments. The present application disclosesa software update for a transport or vehicle 104. The software updatemay include a first portion 116 for the transport 104 and a secondportion 120A/120B through one or more occupant devices 124 of thetransport 104. The second portion 120B may be transferred to thetransport 104 from the one or more occupant devices 124 in response tothe one or more occupant devices 124 being in proximity to the transport104. In response to the software update completed, a notification may besent to the one or more occupant devices 124.

The application solves a potential security problem with transport 104software updates by allocating a portion 120A/120B of a software updateto a user device 124 associated with a transport 104. When the userdevice 124 moves within proximity of the transport 104, the portion 120Bon the user device 124 may be transferred to the transport 104, whichmay then install the complete software update 116/120B. This also putsthe user of the user device 124 in the loop and may allow human approvalto perform the software update. By dividing the software update intomultiple parts 116/120A/120B, any one part being compromised orcorrupted may not alter, invalidate, or change the entire softwareupdate.

A software update may be divided into multiple parts, including at leasta first portion software update 116 and a second portion software update120A/120B. The first portion software update 116 may be related todifferent function software application(s), data structure(s), andmetadata for the transport 104. For example, in one embodiment the firstportion software update 116 may include engine and emission controlswhile the second portion software update 120A/120B may include newprogramming choices for a satellite-=based entertainment system. Aserver 112 transmits the first portion of a software update 116 to atransport or vehicle 104. The first portion software update 116 may betransmitted over any wireless communication technology including but notlimited to BLUETOOTH, WI-FI, or a cellular data connection such as3G/4G/5G or LTE. In some embodiments, the first portion software update116 may be communicated to the transport 104 through a hardware meanssuch as an SD card or USB dongle. The transport or vehicle 104 mayinclude several processors, and the software update may run on a singleprocessor, two or more processors, or all processors. The softwareupdate includes at least two portions, with the first portion beingtransferred directly to the transport 104. The transport 104 may alsoinclude one or more memories, transceivers, receivers, and sensors toallow for the software update to be received.

The server 112 also transfers, either at the same time as the firstportion 116 or at a later time, a second portion of the software update120A to a user device 124 associated with the transport 124. The userdevice 124 may be associated with a user, who may also be associatedwith the transport 104. In other embodiments, a third or more softwareupdate (not shown) may be transmitted to other user devices (not shown),which either do or do not cooperate to transfer those portions to thetransport 104. In other embodiments, the third or more software updatemay also be transferred to the user device 124, so that the user device124 receives multiple portions of the software update. In otherembodiments, the transport 104 may determine one or more (other)compatible transports in proximity to the transport 104 and transfer oneor more portions to the one or more compatible transports. This mayallow portions to be distributed to other transports that may use all orpart of the software update. The transport 104, in some embodiments, maydetermine that the transport 104 uses a same or newer version of thefirst portion software update 116. In response, the transport 104 maynotify the server 112 that the first portion software update 116 may notbe installed.

When the user device 124 moves within proximity to the transport 128,the user device 124 transfers the second portion of the software update120B to the transport or vehicle 104. The proximity 128 may be relatedto a wireless communication range between the user device 124 and thetransport 104. In one embodiment, after the user device 124 receives thesecond portion of the software update 120A, the user device 124wirelessly emits a beacon signal on a random, one-time, or continuousbasis. The user device 124 monitors for a response from the transport104. After receiving the response from the transport 104, the userdevice 124 wirelessly transmits the second portion of the softwareupdate 120B to the transport 104. In other embodiments, the user device124 may transmit an SMS message, an email, or make a call to a phonedevice associated with the transport 104. The transport 104 thenresponds in similar or different fashion to the user device 124, whenenables the user device 124 to wirelessly transmit the second portion ofthe software update 120B to the transport 104.

In another embodiment, the proximity 128 may be related to a geofence.In another embodiment, the proximity 128 may be related to a locationeither the user device 124 or transport 104 is at. In other embodiments,a third or more software update (not shown) may be transmitted fromother user devices (not shown), which either do or do not cooperate totransfer those portions to the transport 104. In other embodiments, athird or more software update 120 may also be transferred from the userdevice 124, so that the user device transfers multiple portions of thesoftware update to the transport or vehicle 104. In some embodiments, amaster software update to the transport 104 may include first, second,and third portions, where the third portion updates one or more occupantdevices of a different type than occupant device(s) 124 receiving thesecond portion of software update 120A. This may allow different typesof occupant devices such as iPhones, Android devices, and tablets ornotebook computers running different operating systems to beconcurrently updated. In some embodiments, the second portion receivedby the one or more devices may include a second portion of the softwareupdate itself. In one embodiment, a user device 124 may receive second120A/120B and third portions of a software update. One of the second120A/120B and third portions of the software update may be usable by theuser device 124, while the other of the second and third portions areintended for a different device. In that case, the user device 124 mayfirst determine it can communicate with the different device. Aftermaking that determination, the user device 124 may then transfer theother of the second and third portions to the different device.Communication may be determined by any known methods including a beaconor other wireless signal, sending a SMS message, email, or making acellular phone call.

In one embodiment, the transport 104 may validate one or more portionsof the software update after the transport 104 has received them, inorder to ensure the integrity of the software update and a reliableupdate process. Received portions of software updates may be stored inone or more memory devices of the transport 104. In one embodiment, atransport 104 may have several computers or processors for differentfunctions, and each computer or processor may have one or moreassociated memory devices. Each received portion of a software updatemay include an identifier that the transport 104 reads in order todetermine which memory device to store the portion to. The identifiermay also include a memory range that specifies a location in the memoryfor storing the software update portion. In another embodiment, thetransport 104 validates the entire software update after all portionshave been received. Validation may include any of integrity checking,combining, compiling, version checking, storing, or any other actionperformed on the software update or software update portions by one ormore computers of the transport 104.

In one embodiment, the transport 104 may install the complete softwareupdate after all portions have been received. Installation may includeparsing the complete software update into portions, associating eachportion with a memory device and/or a location in a memory, and storingeach portion into an appropriate memory device and/or location. Inanother embodiment, the transport 104 installs at least the firstportion 116 when it receives it, and may store one or more otherportions until all portions of the software update have been received.In another embodiment, the transport 104 installs each portion(regardless of how many portions) when it receives it. Once the userdevice 124 has transferred the second (or third, etc) portion(s) of thesoftware update 120 to the transport 104, the transport 104 provides acompletion notification 132 to the user device 124. In anotherembodiment, the transport 104 may provide a completion notification 132to acknowledge receipt of all portions and/or successful installation ofthe complete software update (all portions). The completion notification132 may include an SMS message, an email, an image, or a video thatinforms the user of the user device 124 that the software update hasbeen completed. In another embodiment, the transport 104 may display anotification of completion of the software update on a displayassociated with the transport 104 and/or provide an audio notificationof completion of the software update.

FIG. 1B illustrates an example diagram of data discrepancy resolutionfor a transport 140, according to example embodiments. Transports orvehicles 104 may include sensors including cameras, radar, lidar, orother items that sense location areas outside and in proximity to thetransport 104. Sensors obtain sensor data 144 of these outside items.Sensor data 144 may include camera images of a traffic accident,construction, one or more signs, and/or a road or traffic condition. Thetransport 104 may identify one or more objects at the location from thesensor data 144. It may identify the objects using image interpretationsoftware, pattern matching, optical character recognition (OCR), andcomparison to satellite or other data. In one embodiment, the sensordata 144 may include one or more of a camera image, a notification froma transport entertainment system, and drivetrain sensor data.

In some cases, transports 104 have stored sensor data that is stored onthe transport 104. Stored sensor data may include text, images, video,or various data items. When the transport 104 receives new sensor data144 at a location, it checks to see if the received sensor data 144 isthe same as stored sensor data. Identified objects are compared tostored data on the transport 104. If the received sensor data 144 is thesame as the stored sensor data, the transport 104 continues to receiveand evaluate sensor data 144. However, in some cases, the transport 104may detect a difference between the stored and received 144 sensor data.In that case, the transport 104 may update the data stored on thetransport 104 with the received sensor data 144, and transmits a requestincluding the received sensor data 144 or the difference 148 to a server112. Differences 148 may include camera images of a traffic accident,construction, one or more signs, and/or a road or traffic condition. Inone embodiment, the transport 104 may determine the stored data includesone or more elements that correspond to the difference 148 between thestored data and the sensor data 144, and updates the one or moreelements with the difference 148. The request may include anidentification of the transport 104, a current software level of thetransport 104, and a difference between the current software level andthe latest software update. The latest software update may include asoftware application and one or more of release notes for the latestsoftware update and an installation application.

In one embodiment, providing a request including the sensor data 144 ordifference 148 to a server 112 may include generating, by the transport104, a blockchain transaction to the server 112. The server 112, thetransport 104, and/or the other transports 108A, 108B may be one ofnodes or peers of a blockchain network. The server 112 may also storeany of the sensor data 144, the difference 148, and/or the patch 152 toa shared ledger of the blockchain network.

The server 112 receives the request, and creates a patch 152 includingthe sensor data 144 or the difference 148. The patch 152 may be used toupdate the stored sensor data in transports. The server 112 transmitsthe patch 152 to other transports 108 in proximity to the location wherethe difference was first identified. Any number of transports 108 mayreceive the patch 152, and FIG. 1B illustrates two transports 108A and108B that receive the patch 152. In another embodiment, the transport104 that identified the difference may also receive the patch 152. Insome embodiments, a patch 152 may include other stored data updates,including permanent changes or differences reported by other transports108. In some embodiments, a transport 104, 108A, 108B may displayinformation related to a received patch 152. The displayed informationmay include one or more of a patch 152 name, a version number, a date, acompatible transports list, a size of the patch 152, or the contents ofthe patch 152 itself. The contents may include one or more images,videos, text items, or data items.

In one embodiment, updating the transport 104 with the latest softwareupdate may include identifying one or modules within the latest softwareupdate; associating the one or more modules with the sensor data 144;and updating one or more of an application and a data structure with theone or more modules. In one embodiment, the server 112 may provide thepatch 152 live to other transports 108 that enter proximity range to thelocation, for example within a mile of the location.

In another embodiment, the sensor data 144 and differences 148 mayreflect reverse cases such as a cleared traffic accident, a pothole orother road damage repaired, road barriers removed—in other words atemporary condition that becomes cleared. The stored data in such casesmay be immediately updated to reflect the cleared condition, possiblywithout generating the request and a patch 152 being issued.

In another embodiment, a transport 104 or a server 112 may determine thedifferences 148 between the sensor data 144 and the stored data asbefore, but is able to estimate a time to clear based on the differences148. The time to clear may be determined by comparing the sensor data144 to a series of stored images that display different trafficaccidents or road repair of varying “severity”, each with an associatedrepair time. By matching a closest stored image/repair time to thesensor data 144, a most likely repair time may be determined. In oneembodiment, the transport 104 may provide the estimated repair time tothe server 112 or other transports 108A, 108B in proximity to thelocation. The other transports 108A, 108B may be able to take advantageof this information by delaying starting out until the repair oraccident is cleared, or taking a different route that bypasses thelocation.

For example, one or more sensor(s) of a transport 104 may detect a newstreet sign in a new neighborhood. The street sign may have been justrecently installed, and may reflect a new street name. The transport 104may include a navigation computer that includes various maps includingstreets and street names. When the sensor(s) observe the new street name(“Main Street”), the transport 104 may check its' stored data to see ifthe street name is present. Because the stored data was installed to thetransport 104 before the street name was assigned, the new street nameis not found in the stored data. Therefore, the street name at thelocation becomes a difference 148 that the transport 104 sends to theserver 112. The server 112 then creates a patch 152 that includes thenew street name (and possibly other differences 148 received since aprevious patch 152 was issued), and distributes the patch 152 includingthe new street name to other transports 108A, 108B that are in proximityto the transport 104 when it first observed the street name. The othertransports 108A, 108B, in response, update their own stored data toinclude the patch 152 and the new street name.

FIG. 1C illustrates an example diagram of transport behavior observation160, according to example embodiments. Transports 104 include varioussensors, including cameras, that may observe other transports 108 inproximity. In most embodiments, “in proximity” means within a line ofsight of the transport 104, and preferably close enough to observedetails of the other transport 108 and how it is being operated. Atransport's behavior relates to how it is being operated, and includes atransport's speed, acceleration, traction in weather, handling, seatingcapacity, load carrying capacity, towing capacity, and the like.Transports have performance characteristics that depend on the design ofa transport, its intended use, price, and region where purchased. Atransport's performance may also be related to characteristics of adriver—such as a driver's eyesight, reaction time, confidence, anddriving ability. Thus, a transport's actual performance is a combinationof both a transport's automotive characteristics and performance and adriver's characteristics. In some embodiments, the performance of atransport is limited by automotive characteristics of the transportitself, while in other embodiments, the performance of a transport islimited by limitations of the driver. In yet other embodiments, theperformance of a transport may be limited by both automotivecharacteristics of the transport and by limitations of the driver.

Multiple transports 104, identified as transport or vehicle 104A andtransport or vehicle 104B, are in proximity to another transport 108.Each of the transports 104A, 104B, 108 may be a same or different type.In FIG. 1C, transports 104 are passenger vehicles while transport 108 isa pickup truck towing a large 5′-wheel trailer. Each of the transports104A, 104B includes side-vision cameras that observe the transport 108.Transport 104A observes the other transport 164A and transport 104Bobserves the other transport 164B.

Each transport 104A, 104B independently observes 164A, 164B how theother transport 108 is being operated, as described previously, andmakes a determination the other transport 108 is not being operated asintended. The determination may be that the other transport 108 isoverloaded in some fashion, the other transport 108 is in obvious needof repair (emitting a very excessive amount of exhaust smoke, forexample), the other transport 108 is being accelerated too slowly, hasimproper tire pressure in one or more tires, has one or more blockedmirrors, or is being operated in any other fashion that may be not asthe other transport 108 was intended to operate. Once the transport104A, 104B makes this determination, the transport 104A, 104B providesan indication or transaction 168 to a server 112. In one embodiment,each transport 104A, 104B examines itself using the same behaviorcriteria as the other transport 108, and provides a notification toitself or a device associated with the transport 104 similar to whatwould be provided to the other transport 108, as described herein.

The indication or transaction 168 (i.e. indication or transaction 168Afrom transport 104A and indication or transaction 168B from transport104B) provides an identification of the other transport 108 as well as abehavior of the other transport 108 not as intended. The identificationof the other transport 108 may include a camera image, a Vehicle IDNumber (VIN Number), a license plate number, a state of registration(either the US state where the vehicle is registered as well as anindication if the registration is current), and/or a physicaldescription (i.e. model year, manufacturer, model, color, etc) of anexterior of the other transport 108. The identification allows theserver 112 to uniquely identify the other transport 108 from all othertransports 104, 108 so that a notification 172 may be sent to the othertransport 108 or a device associated with the other transport 108.

In one embodiment, indications 168A, 168B are blockchain transactions,where a blockchain network includes the transports 104A, 104B and theserver 112. The blockchain transactions 168A, 168B provide informationto the server 112 and are stored to a shared ledger associated with theblockchain network.

In another embodiment, a transport 104 may identify one or more othertransports 108 that use a software module, and obtain a current softwarelevel for the software module from one or more other transports 108. Inresponse to determining the current software level from anothertransport 108 is more recent than a current software level for the othertransport 108, the transport 104 may request the more recent softwareupdate from another transport 108, install the more recent softwareupdate, and in response to the transport 104 determines the currentsoftware level from another transport 108 is older than the currentsoftware level for the other transport 108, the transport 104 transfersa software update corresponding to the current software level for theother transport 108 to another transport 108 that includes an oldersoftware level.

The server 112 receives the indications or transactions 168 frommultiple transports or vehicles 104. Although two such transports orvehicles 104A, 104B are shown in FIG. 1C, there may be any number oftransports 104 providing such information as long as two or moretransports 104 are involved. The server 112 forms a consensus afterreceiving indications or transactions 168 from multiple transports 104.In one embodiment, the server 112 forms a first consensus afterreceiving multiple indications or transactions 168, and performsadditional consensus after receiving a next following indication ortransaction 168. Each of the received indications or transactions 168used for a consensus must apply to a same other transport 108. In oneembodiment, a consensus may be formed if a majority of the receivedindications or transactions 168 apply to a same other transport 108. Inanother embodiment, a consensus may be formed if a majority of thereceived indications or transactions 168 apply to a same other transport108, and a same behavior is identified. In another embodiment, a samebehavior may be identified by multiple transports 104 prior to formingthe consensus. In one embodiment, the server 112 matches a behaviorpattern associated with the other transport 108 to a different type oftransport than the other transport 108 and/or a different way ofoperating the other transport 108. For a blockchain network, a consensusmay be performed by a majority of validating nodes or peers.

Once a consensus has been performed by the server 112, the server 112transmits a notification 172 to the other transport 108 and/or one ormore devices (such as cell phones/smart phones) associated with theother transport 108. The notification 172 may provide information aboutthe behavior not as intended, how to correct the behavior not asintended, a new other transport 108 type or description, or a proposedchange or modification to the other transport 108. In one embodiment,the notification 172 may include a different type of transport than theother transport 108 and/or a different way of operating the othertransport 108. For example, the notification 172 may indicate the othertransport 108 may be overloaded, encourage a driver of the othertransport 108 to remove cargo or passengers from the other transport108, recommend and upgrade to a newer or different transport 108 typewith higher load capacity, or recommend the other transport 108 driverto select a different transmission gear ratio on a control of the othertransport 108. In one embodiment, the notification 172 may include anupgrade recommendation for the other transport 108, including a featureor software upgrade. In another embodiment, the notification 172 mayinclude a downgrade recommendation for the other transport 108,including a feature or software downgrade.

FIG. 2A illustrates a transport network diagram 200, according toexample embodiments. The network comprises elements including atransport node 202 including a processor 204, as well as a transportnode 202′ including a processor 204′. The transport nodes 202, 202′communicate with one another via the processors 204, 204′, as well asother elements (not shown) including transceivers, transmitters,receivers, storage, sensors and other elements capable of providingcommunication. The communication between the transport nodes 202, 202′can occur directly, via a private and/or a public network (not shown) orvia other transport nodes and elements comprising one or more of aprocessor, memory, and software. Although depicted as single transportnodes and processors, a plurality of transport nodes and processors maybe present. One or more of the applications, features, steps, solutions,etc., described and/or depicted herein may be utilized and/or providedby the instant elements.

FIG. 2B illustrates another transport network diagram 210, according toexample embodiments. The network comprises elements including atransport node 202 including a processor 204, as well as a transportnode 202′ including a processor 204′. The transport nodes 202, 202′communicate with one another via the processors 204, 204′, as well asother elements (not shown) including transceivers, transmitters,receivers, storage, sensors and other elements capable of providingcommunication. The communication between the transport nodes 202, 202′can occur directly, via a private and/or a public network (not shown) orvia other transport nodes and elements comprising one or more of aprocessor, memory, and software. The processors 204, 204′ can furthercommunicate with one or more elements 230 including sensor 212, wireddevice 214, wireless device 216, database 218, mobile phone 220,transport node 222, computer 224, I/O device 226 and voice application228. The processors 204, 204′ can further communicate with elementscomprising one or more of a processor, memory, and software.

Although depicted as single transport nodes, processors and elements, aplurality of transport nodes, processors and elements may be present.Information or communication can occur to and/or from any of theprocessors 204, 204′ and elements 230. For example, the mobile phone 220may provide information to the processor 204 which may initiate thetransport node 202 to take an action, may further provide theinformation or additional information to the processor 204′ which mayinitiate the transport node 202′ to take an action, may further providethe information or additional information to the mobile phone 220, thetransport node 222, and/or the computer 224. One or more of theapplications, features, steps, solutions, etc., described and/ordepicted herein may be utilized and/or provided by the instant elements.

FIG. 2C illustrates yet another transport network diagram 240, accordingto example embodiments. The network comprises elements including atransport node 202 including a processor 204 and a non-transitorycomputer readable medium 242C. The processor 204 is communicably coupledto the computer readable medium 242C and elements 230 (which weredepicted in FIG. 2B).

The processor 204 performs one or more of the following steps. At step244C, the transport memory receives a first portion of a software updatefrom a server. The software update includes at least two portions. Thefirst portion is transferred to the transport by the server, and asecond portion is provided to a user device. At step 246C, the transportmemory receives a second portion of the software update from a userdevice in proximity to the transport. At step 248C, a transportprocessor performs the software update. Finally, at step 250C, thetransport provides notification of completion of the software update.

FIG. 2D illustrates yet another transport network diagram 260, accordingto example embodiments. The network comprises elements including atransport node 202 including a processor 204 and a non-transitorycomputer readable medium 242D. The processor 204 is communicably coupledto the computer readable medium 242D and elements 230 (which weredepicted in FIG. 2B).

The processor 204 performs one or more of the following steps. At step244D, the transport detects a difference between inside and outsidesensor data. The inside data is data stored on the transport, while theoutside data is sensor data reflecting the environment outside thetransport. At step 246D, the transport updates the data stored on thetransport with the difference. In one embodiment, the transporttransmits a request including the sensor data to a server. The serverthen creates a patch including the sensor data, and transmits the patchto other transports in proximity to a location outside the transport.

FIG. 2E illustrates yet another transport network diagram 270, accordingto example embodiments. The network comprises elements including atransport node 202 including a processor 204 and a non-transitorycomputer readable medium 242E. The processor 204 is communicably coupledto the computer readable medium 242E and elements 230 (which weredepicted in FIG. 2B).

The processor 204 performs one or more of the following steps. At step244E, a server receives one or more indications of another transportoperated in a different manner than intended. The indications include anidentifier of the other transport and an identification of one or moreways the other transport is being operated in a different manner thanintended. At step 246E, the server forms a consensus from the receivedindications. At step 248E, the server transmits a notification to othertransports and a device associated with the other transport. Thenotification may provide a recommendation or suggestion of an alternatetype of transport.

The processors and/or computer readable media may fully or partiallyreside in the interior or exterior of the transport nodes. The steps orfeatures stored in the computer readable media may be fully or partiallyperformed by any of the processors and/or elements in any order.Additionally, one or more steps or features may be added, omitted,combined, performed at a later time, etc.

FIG. 3A illustrates a flow diagram 300, according to exampleembodiments. Referring to FIG. 3A, at block 302, the transport memoryreceives a first portion of a software update from a server. Thesoftware update includes at least two portions. The first portion istransferred to the transport by the server, and a second portion isprovided to a user device. At block 304, the transport memory receives asecond portion of the software update from a user device in proximity tothe transport. At block 306, a transport processor performs the softwareupdate. Finally, at block 308, the transport provides notification ofcompletion of the software update.

FIG. 3B illustrates another flow diagram 320, according to exampleembodiments. Referring to FIG. 3B, at block 322, the transport detects adifference between inside and outside sensor data. The inside data isdata stored on the transport, while the outside data is sensor datareflecting the environment outside the transport. At block 324, thetransport updates the data stored on the transport with the difference.In one embodiment, the transport transmits a request including thesensor data to a server. The server then creates a patch including thesensor data, and transmits the patch to other transports in proximity toa location outside the transport.

FIG. 3C illustrates yet another flow diagram 340, according to exampleembodiments. Referring to FIG. 3C, at block 342, a server receives oneor more indications of another transport operated in a different mannerthan intended. The indications include an identifier of the othertransport and an identification of one or more ways the other transportis being operated in a different manner than intended. At block 344, theserver forms a consensus from the received indications. Finally, atblock 346, the server transmits a notification to other transports and adevice associated with the other transport. The notification may providea recommendation or suggestion of an alternate type of transport.

FIG. 4 illustrates a machine learning transport network diagram 400,according to example embodiments. The network 400 includes a transportnode 402 that interfaces with a machine learning subsystem 406. Thetransport node includes one or more sensors 404.

The machine learning subsystem 406 contains a learning model 408 whichis a mathematical artifact created by a machine learning training system410 that generates predictions by finding patterns in one or moretraining data sets. In some embodiments, the machine learning subsystem406 resides in the transport node 402. In other embodiments, the machinelearning subsystem 406 resides outside of the transport node 402.

The transport node 402 sends data from the one or more sensors 404 tothe machine learning subsystem 406. The machine learning subsystem 406provides the one or more sensor 404 data to the learning model 408 whichreturns one or more predictions. The machine learning subsystem 406sends one or more instructions to the transport node 402 based on thepredictions from the learning model 408.

In a further embodiment, the transport node 402 may send the one or moresensor 404 data to the machine learning training system 410. In yetanother embodiment, the machine learning subsystem 406 may sent thesensor 404 data to the machine learning subsystem 410. One or more ofthe applications, features, steps, solutions, etc., described and/ordepicted herein may utilize the machine learning network 400 asdescribed herein.

FIG. 5A illustrates an example vehicle configuration 500 for managingdatabase transactions associated with a vehicle, according to exampleembodiments. Referring to FIG. 5A, as a particular transport/vehicle 525is engaged in transactions (e.g., vehicle service, dealer transactions,delivery/pickup, transportation services, etc.), the vehicle may receiveassets 510 and/or expel/transfer assets 512 according to atransaction(s). A transport processor 526 resides in the vehicle 525 andcommunication exists between the transport processor 526, a database530, a transport processor 526 and the transaction module 520. Thetransaction module 520 may record information, such as assets, parties,credits, service descriptions, date, time, location, results,notifications, unexpected events, etc. Those transactions in thetransaction module 520 may be replicated into a database 530. Thedatabase 530 can be one of a SQL database, an RDBMS, a relationaldatabase, a non-relational database, a blockchain, a distributed ledger,and may be on board the transport, may be off board the transport, maybe accessible directly and/or through a network, or be accessible to thetransport.

FIG. 5B illustrates an example vehicle configuration 550 for managingdatabase transactions conducted among various vehicles, according toexample embodiments. The vehicle 525 may engage with another vehicle 508to perform various actions such as to share, transfer, acquire servicecalls, etc. when the vehicle has reached a status where the servicesneed to be shared with another vehicle. For example, the vehicle 508 maybe due for a battery charge and/or may have an issue with a tire and maybe in route to pick up a package for delivery. A transport processor 528resides in the vehicle 508 and communication exists between thetransport processor 528, a database 554, a transport processor 528 andthe transaction module 552. The vehicle 508 may notify another vehicle525 which is in its network and which operates on its blockchain memberservice. A transport processor 526 resides in the vehicle 525 andcommunication exists between the transport processor 526, a database530, the transport processor 526 and a transaction module 520. Thevehicle 525 may then receive the information via a wirelesscommunication request to perform the package pickup from the vehicle 508and/or from a server (not shown). The transactions are logged in thetransaction modules 552 and 520 of both vehicles. The credits aretransferred from vehicle 508 to vehicle 525 and the record of thetransferred service is logged in the database 530/554 assuming that theblockchains are different from one another, or, are logged in the sameblockchain used by all members. The database 554 can be one of a SQLdatabase, an RDBMS, a relational database, a non-relational database, ablockchain, a distributed ledger, and may be on board the transport, maybe off board the transport, may be accessible directly and/or through anetwork.

FIG. 6A illustrates a blockchain architecture configuration 600,according to example embodiments. Referring to FIG. 6A, the blockchainarchitecture 600 may include certain blockchain elements, for example, agroup of blockchain member nodes 602-606 as part of a blockchain group610. In one example embodiment, a permissioned blockchain is notaccessible to all parties but only to those members with permissionedaccess to the blockchain data. The blockchain nodes participate in anumber of activities, such as blockchain entry addition and validationprocess (consensus). One or more of the blockchain nodes may endorseentries based on an endorsement policy and may provide an orderingservice for all blockchain nodes. A blockchain node may initiate ablockchain action (such as an authentication) and seek to write to ablockchain immutable ledger stored in the blockchain, a copy of whichmay also be stored on the underpinning physical infrastructure.

The blockchain transactions 620 are stored in memory of computers as thetransactions are received and approved by the consensus model dictatedby the members' nodes. Approved transactions 626 are stored in currentblocks of the blockchain and committed to the blockchain via a committalprocedure which includes performing a hash of the data contents of thetransactions in a current block and referencing a previous hash of aprevious block. Within the blockchain, one or more smart contracts 630may exist that define the terms of transaction agreements and actionsincluded in smart contract executable application code 632, such asregistered recipients, vehicle features, requirements, permissions,sensor thresholds, etc. The code may be configured to identify whetherrequesting entities are registered to receive vehicle services, whatservice features they are entitled/required to receive given theirprofile statuses and whether to monitor their actions in subsequentevents. For example, when a service event occurs and a user is riding inthe vehicle, the sensor data monitoring may be triggered, and a certainparameter, such as a vehicle charge level, may be identified as beingabove/below a particular threshold for a particular period of time, thenthe result may be a change to a current status which requires an alertto be sent to the managing party (i.e., vehicle owner, vehicle operator,server, etc.) so the service can be identified and stored for reference.The vehicle sensor data collected may be based on types of sensor dataused to collect information about vehicle's status. The sensor data mayalso be the basis for the vehicle event data 634, such as a location(s)to be traveled, an average speed, a top speed, acceleration rates,whether there were any collisions, was the expected route taken, what isthe next destination, whether safety measures are in place, whether thevehicle has enough charge/fuel, etc. All such information may be thebasis of smart contract terms 630, which are then stored in ablockchain. For example, sensor thresholds stored in the smart contractcan be used as the basis for whether a detected service is necessary andwhen and where the service should be performed.

FIG. 6B illustrates a shared ledger configuration, according to exampleembodiments. Referring to FIG. 6B, the blockchain logic example 640includes a blockchain application interface 642 as an API or plug-inapplication that links to the computing device and execution platformfor a particular transaction. The blockchain configuration 640 mayinclude one or more applications which are linked to applicationprogramming interfaces (APIs) to access and execute storedprogram/application code (e.g., smart contract executable code, smartcontracts, etc.) which can be created according to a customizedconfiguration sought by participants and can maintain their own state,control their own assets, and receive external information. This can bedeployed as an entry and installed, via appending to the distributedledger, on all blockchain nodes.

The smart contract application code 644 provides a basis for theblockchain transactions by establishing application code which whenexecuted causes the transaction terms and conditions to become active.The smart contract 630, when executed, causes certain approvedtransactions 626 to be generated, which are then forwarded to theblockchain platform 652. The platform includes a security/authorization658, computing devices which execute the transaction management 656 anda storage portion 654 as a memory that stores transactions and smartcontracts in the blockchain.

The blockchain platform may include various layers of blockchain data,services (e.g., cryptographic trust services, virtual executionenvironment, etc.), and underpinning physical computer infrastructurethat may be used to receive and store new entries and provide access toauditors which are seeking to access data entries. The blockchain mayexpose an interface that provides access to the virtual executionenvironment necessary to process the program code and engage thephysical infrastructure. Cryptographic trust services may be used toverify entries such as asset exchange entries and keep informationprivate.

The blockchain architecture configuration of FIGS. 6A and 6B may processand execute program/application code via one or more interfaces exposed,and services provided, by the blockchain platform. As a non-limitingexample, smart contracts may be created to execute reminders, updates,and/or other notifications subject to the changes, updates, etc. Thesmart contracts can themselves be used to identify rules associated withauthorization and access requirements and usage of the ledger. Forexample, the information may include a new entry, which may be processedby one or more processing entities (e.g., processors, virtual machines,etc.) included in the blockchain layer. The result may include adecision to reject or approve the new entry based on the criteriadefined in the smart contract and/or a consensus of the peers. Thephysical infrastructure may be utilized to retrieve any of the data orinformation described herein.

Within smart contract executable code, a smart contract may be createdvia a high-level application and programming language, and then writtento a block in the blockchain. The smart contract may include executablecode which is registered, stored, and/or replicated with a blockchain(e.g., distributed network of blockchain peers). An entry is anexecution of the smart contract code which can be performed in responseto conditions associated with the smart contract being satisfied. Theexecuting of the smart contract may trigger a trusted modification(s) toa state of a digital blockchain ledger. The modification(s) to theblockchain ledger caused by the smart contract execution may beautomatically replicated throughout the distributed network ofblockchain peers through one or more consensus protocols.

The smart contract may write data to the blockchain in the format ofkey-value pairs. Furthermore, the smart contract code can read thevalues stored in a blockchain and use them in application operations.The smart contract code can write the output of various logic operationsinto the blockchain. The code may be used to create a temporary datastructure in a virtual machine or other computing platform. Data writtento the blockchain can be public and/or can be encrypted and maintainedas private. The temporary data that is used/generated by the smartcontract is held in memory by the supplied execution environment, thendeleted once the data needed for the blockchain is identified.

A smart contract executable code may include the code interpretation ofa smart contract, with additional features. As described herein, thesmart contract executable code may be program code deployed on acomputing network, where it is executed and validated by chainvalidators together during a consensus process. The smart contractexecutable code receives a hash and retrieves from the blockchain a hashassociated with the data template created by use of a previously storedfeature extractor. If the hashes of the hash identifier and the hashcreated from the stored identifier template data match, then the smartcontract executable code sends an authorization key to the requestedservice. The smart contract executable code may write to the blockchaindata associated with the cryptographic details.

FIG. 6C illustrates a blockchain configuration for storing blockchaintransaction data, according to example embodiments. Referring to FIG.6C, the example configuration 660 provides for the vehicle 662, the userdevice 664 and a server 666 sharing information with a distributedledger (i.e., blockchain) 668. The server may represent a serviceprovider entity inquiring with a vehicle service provider to share userprofile rating information in the event that a known and establisheduser profile is attempting to rent a vehicle with an established ratedprofile. The server 666 may be receiving and processing data related toa vehicle's service requirements. As the service events occur, such asthe vehicle sensor data indicates a need for fuel/charge, a maintenanceservice, etc., a smart contract may be used to invoke rules, thresholds,sensor information gathering, etc., which may be used to invoke thevehicle service event. The blockchain transaction data 670 is saved foreach transaction, such as the access event, the subsequent updates to avehicle's service status, event updates, etc. The transactions mayinclude the parties, the requirements (e.g., 18 years of age, serviceeligible candidate, valid driver's license, etc.), compensation levels,the distance traveled during the event, the registered recipientspermitted to access the event and host a vehicle service,rights/permissions, sensor data retrieved during the vehicle eventoperation to log details of the next service event and identify avehicle's condition status, and thresholds used to make determinationsabout whether the service event was completed and whether the vehicle'scondition status has changed.

FIG. 6D illustrates blockchain blocks 680 that can be added to adistributed ledger, according to example embodiments, and contents ofblock structures 682A to 682 n. Referring to FIG. 6D, clients (notshown) may submit entries to blockchain nodes to enact activity on theblockchain. As an example, clients may be applications that act onbehalf of a requester, such as a device, person or entity to proposeentries for the blockchain. The plurality of blockchain peers (e.g.,blockchain nodes) may maintain a state of the blockchain network and acopy of the distributed ledger. Different types of blockchainnodes/peers may be present in the blockchain network including endorsingpeers which simulate and endorse entries proposed by clients andcommitting peers which verify endorsements, validate entries, and commitentries to the distributed ledger. In this example, the blockchain nodesmay perform the role of endorser node, committer node, or both.

The instant system includes a blockchain which stores immutable,sequenced records in blocks, and a state database (current world state)maintaining a current state of the blockchain. One distributed ledgermay exist per channel and each peer maintains its own copy of thedistributed ledger for each channel of which they are a member. Theinstant blockchain is an entry log, structured as hash-linked blockswhere each block contains a sequence of N entries. Blocks may includevarious components such as those shown in FIG. 6D. The linking of theblocks may be generated by adding a hash of a prior block's headerwithin a block header of a current block. In this way, all entries onthe blockchain are sequenced and cryptographically linked togetherpreventing tampering with blockchain data without breaking the hashlinks. Furthermore, because of the links, the latest block in theblockchain represents every entry that has come before it. The instantblockchain may be stored on a peer file system (local or attachedstorage), which supports an append-only blockchain workload.

The current state of the blockchain and the distributed ledger may bestored in the state database. Here, the current state data representsthe latest values for all keys ever included in the chain entry log ofthe blockchain. Smart contract executable code invocations executeentries against the current state in the state database. To make thesesmart contract executable code interactions extremely efficient, thelatest values of all keys are stored in the state database. The statedatabase may include an indexed view into the entry log of theblockchain, it can therefore be regenerated from the chain at any time.The state database may automatically get recovered (or generated ifneeded) upon peer startup, before entries are accepted.

Endorsing nodes receive entries from clients and endorse the entry basedon simulated results. Endorsing nodes hold smart contracts whichsimulate the entry proposals. When an endorsing node endorses an entry,the endorsing nodes creates an entry endorsement which is a signedresponse from the endorsing node to the client application indicatingthe endorsement of the simulated entry. The method of endorsing an entrydepends on an endorsement policy which may be specified within smartcontract executable code. An example of an endorsement policy is “themajority of endorsing peers must endorse the entry.” Different channelsmay have different endorsement policies. Endorsed entries are forward bythe client application to an ordering service.

The ordering service accepts endorsed entries, orders them into a block,and delivers the blocks to the committing peers. For example, theordering service may initiate a new block when a threshold of entrieshas been reached, a timer times out, or another condition. In thisexample, blockchain node is a committing peer that has received a datablock 682A for storage on the blockchain. The ordering service may bemade up of a cluster of orderers. The ordering service does not processentries, smart contracts, or maintain the shared ledger. Rather, theordering service may accept the endorsed entries and specifies the orderin which those entries are committed to the distributed ledger. Thearchitecture of the blockchain network may be designed such that thespecific implementation of ‘ordering’ (e.g., Solo, Kafka, BFT, etc.)becomes a pluggable component.

Entries are written to the distributed ledger in a consistent order. Theorder of entries is established to ensure that the updates to the statedatabase are valid when they are committed to the network. Unlike acryptocurrency blockchain system (e.g., Bitcoin, etc.) where orderingoccurs through the solving of a cryptographic puzzle, or mining, in thisexample the parties of the distributed ledger may choose the orderingmechanism that best suits that network.

Referring to FIG. 6D, a block 682A (also referred to as a data block)that is stored on the blockchain and/or the distributed ledger mayinclude multiple data segments such as a block header 684A to 684 n,transaction specific data 686A to 686 n, and block metadata 688A to 688n. It should be appreciated that the various depicted blocks and theircontents, such as block 682A and its contents are merely for purposes ofan example and are not meant to limit the scope of the exampleembodiments. In some cases, both the block header 684A and the blockmetadata 688A may be smaller than the transaction specific data 686Awhich stores entry data; however, this is not a requirement. The block682A may store transactional information of N entries (e.g., 100, 500,1000, 2000, 3000, etc.) within the block data 690A to 690 n. The block682A may also include a link to a previous block (e.g., on theblockchain) within the block header 684A. In particular, the blockheader 684A may include a hash of a previous block's header. The blockheader 684A may also include a unique block number, a hash of the blockdata 690A of the current block 682A, and the like. The block number ofthe block 682A may be unique and assigned in an incremental/sequentialorder starting from zero. The first block in the blockchain may bereferred to as a genesis block which includes information about theblockchain, its members, the data stored therein, etc.

The block data 690A may store entry information of each entry that isrecorded within the block. For example, the entry data may include oneor more of a type of the entry, a version, a timestamp, a channel ID ofthe distributed ledger, an entry ID, an epoch, a payload visibility, asmart contract executable code path (deploy tx), a smart contractexecutable code name, a smart contract executable code version, input(smart contract executable code and functions), a client (creator)identify such as a public key and certificate, a signature of theclient, identities of endorsers, endorser signatures, a proposal hash,smart contract executable code events, response status, namespace, aread set (list of key and version read by the entry, etc.), a write set(list of key and value, etc.), a start key, an end key, a list of keys,a Merkel tree query summary, and the like. The entry data may be storedfor each of the N entries.

In some embodiments, the block data 690A may also store transactionspecific data 686A which adds additional information to the hash-linkedchain of blocks in the blockchain. Accordingly, the data 686A can bestored in an immutable log of blocks on the distributed ledger. Some ofthe benefits of storing such data 686A are reflected in the variousembodiments disclosed and depicted herein. The block metadata 688A maystore multiple fields of metadata (e.g., as a byte array, etc.).Metadata fields may include signature on block creation, a reference toa last configuration block, an entry filter identifying valid andinvalid entries within the block, last offset persisted of an orderingservice that ordered the block, and the like. The signature, the lastconfiguration block, and the orderer metadata may be added by theordering service. Meanwhile, a committer of the block (such as ablockchain node) may add validity/invalidity information based on anendorsement policy, verification of read/write sets, and the like. Theentry filter may include a byte array of a size equal to the number ofentries in the block data 690A and a validation code identifying whetheran entry was valid/invalid.

The other blocks 682B to 682 n in the blockchain also have headers,files, and values. However, unlike the first block 682A, each of theheaders 684A to 684 n in the other blocks includes the hash value of animmediately preceding block. The hash value of the immediately precedingblock may be just the hash of the header of the previous block or may bethe hash value of the entire previous block. By including the hash valueof a preceding block in each of the remaining blocks, a trace can beperformed from the Nth block back to the genesis block (and theassociated original file) on a block-by-block basis, as indicated byarrows 692, to establish an auditable and immutable chain-of-custody.

The above embodiments may be implemented in hardware, in a computerprogram executed by a processor, in firmware, or in a combination of theabove. A computer program may be embodied on a computer readable medium,such as a storage medium. For example, a computer program may reside inrandom access memory (“RAM”), flash memory, read-only memory (“ROM”),erasable programmable read-only memory (“EPROM”), electrically erasableprogrammable read-only memory (“EEPROM”), registers, hard disk, aremovable disk, a compact disk read-only memory (“CD-ROM”), or any otherform of storage medium known in the art.

An exemplary storage medium may be coupled to the processor such thatthe processor may read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anapplication specific integrated circuit (“ASIC”). In the alternative,the processor and the storage medium may reside as discrete components.For example, FIG. 7 illustrates an example computer system architecture700, which may represent or be integrated in any of the above-describedcomponents, etc.

FIG. 7 is not intended to suggest any limitation as to the scope of useor functionality of embodiments of the application described herein.Regardless, the computing node 700 is capable of being implementedand/or performing any of the functionality set forth hereinabove.

In computing node 700 there is a computer system/server 702, which isoperational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 702 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 702 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 702 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 7, computer system/server 702 in cloud computing node700 is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 702 may include, but are notlimited to, one or more processors or processing units 704, a systemmemory 706, and a bus that couples various system components includingsystem memory 706 to processor 704.

The bus represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnects (PCI) bus.

Computer system/server 702 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 702, and it includes both volatileand non-volatile media, removable and non-removable media. System memory706, in one embodiment, implements the flow diagrams of the otherfigures. The system memory 706 can include computer system readablemedia in the form of volatile memory, such as random-access memory (RAM)708 and/or cache memory 710. Computer system/server 702 may furtherinclude other removable/non-removable, volatile/non-volatile computersystem storage media. By way of example only, memory 706 can be providedfor reading from and writing to a non-removable, non-volatile magneticmedia (not shown and typically called a “hard drive”). Although notshown, a magnetic disk drive for reading from and writing to aremovable, non-volatile magnetic disk (e.g., a “floppy disk”), and anoptical disk drive for reading from or writing to a removable,non-volatile optical disk such as a CD-ROM, DVD-ROM or other opticalmedia can be provided. In such instances, each can be connected to thebus by one or more data media interfaces. As will be further depictedand described below, memory 706 may include at least one program producthaving a set (e.g., at least one) of program modules that are configuredto carry out the functions of various embodiments of the application.

Program/utility, having a set (at least one) of program modules, may bestored in memory 706 by way of example, and not limitation, as well asan operating system, one or more application programs, other programmodules, and program data. Each of the operating system, one or moreapplication programs, other program modules, and program data or somecombination thereof, may include an implementation of a networkingenvironment. Program modules generally carry out the functions and/ormethodologies of various embodiments of the application as describedherein.

As will be appreciated by one skilled in the art, aspects of the presentapplication may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present application may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present application may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Computer system/server 702 may also communicate with one or moreexternal devices via an I/O device 712 (such as an I/O adapter), whichmay include a keyboard, a pointing device, a display, a voicerecognition module, etc., one or more devices that enable a user tointeract with computer system/server 702, and/or any devices (e.g.,network card, modem, etc.) that enable computer system/server 702 tocommunicate with one or more other computing devices. Such communicationcan occur via I/O interfaces of the device 712. Still yet, computersystem/server 702 can communicate with one or more networks such as alocal area network (LAN), a general wide area network (WAN), and/or apublic network (e.g., the Internet) via a network adapter. As depicted,device 712 communicates with the other components of computersystem/server 702 via a bus. It should be understood that although notshown, other hardware and/or software components could be used inconjunction with computer system/server 702. Examples, include, but arenot limited to: microcode, device drivers, redundant processing units,external disk drive arrays, RAID systems, tape drives, and data archivalstorage systems, etc.

Although an exemplary embodiment of at least one of a system, method,and non-transitory computer readable medium has been illustrated in theaccompanied drawings and described in the foregoing detaileddescription, it will be understood that the application is not limitedto the embodiments disclosed, but is capable of numerous rearrangements,modifications, and substitutions as set forth and defined by thefollowing claims. For example, the capabilities of the system of thevarious figures can be performed by one or more of the modules orcomponents described herein or in a distributed architecture and mayinclude a transmitter, receiver or pair of both. For example, all orpart of the functionality performed by the individual modules, may beperformed by one or more of these modules. Further, the functionalitydescribed herein may be performed at various times and in relation tovarious events, internal or external to the modules or components. Also,the information sent between various modules can be sent between themodules via at least one of: a data network, the Internet, a voicenetwork, an Internet Protocol network, a wireless device, a wired deviceand/or via plurality of protocols. Also, the messages sent or receivedby any of the modules may be sent or received directly and/or via one ormore of the other modules.

One skilled in the art will appreciate that a “system” could be embodiedas a personal computer, a server, a console, a personal digitalassistant (PDA), a cell phone, a tablet computing device, a smartphoneor any other suitable computing device, or combination of devices.Presenting the above-described functions as being performed by a“system” is not intended to limit the scope of the present applicationin any way but is intended to provide one example of many embodiments.Indeed, methods, systems and apparatuses disclosed herein may beimplemented in localized and distributed forms consistent with computingtechnology.

It should be noted that some of the system features described in thisspecification have been presented as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom verylarge-scale integration (VLSI) circuits or gate arrays, off-the-shelfsemiconductors such as logic chips, transistors, or other discretecomponents. A module may also be implemented in programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices, graphics processing units, or thelike.

A module may also beat least partially implemented in software forexecution by various types of processors. An identified unit ofexecutable code may, for instance, comprise one or more physical orlogical blocks of computer instructions that may, for instance, beorganized as an object, procedure, or function. Nevertheless, theexecutables of an identified module need not be physically locatedtogether but may comprise disparate instructions stored in differentlocations which, when joined logically together, comprise the module andachieve the stated purpose for the module. Further, modules may bestored on a computer-readable medium, which may be, for instance, a harddisk drive, flash device, random access memory (RAM), tape, or any othersuch medium used to store data.

Indeed, a module of executable code could be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within modules and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork.

It will be readily understood that the components of the application, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations.Thus, the detailed description of the embodiments is not intended tolimit the scope of the application as claimed but is merelyrepresentative of selected embodiments of the application.

One having ordinary skill in the art will readily understand that theabove may be practiced with steps in a different order, and/or withhardware elements in configurations that are different than those whichare disclosed. Therefore, although the application has been describedbased upon these preferred embodiments, it would be apparent to those ofskill in the art that certain modifications, variations, and alternativeconstructions would be apparent.

While preferred embodiments of the present application have beendescribed, it is to be understood that the embodiments described areillustrative only and the scope of the application is to be definedsolely by the appended claims when considered with a full range ofequivalents and modifications (e.g., protocols, hardware devices,software platforms etc.) thereto.

What is claimed is:
 1. A method, comprising: receiving indications froma plurality of transports, by a server, of another transport inproximity to the plurality of transports, each indication comprising anidentifier of the other transport and an identification of one or moreways the other transport is being operated in a different manner thanintended; forming a consensus, by the server, from the indications fromthe plurality of transports; in response to the consensus, determining,by the server, a behavior pattern comprising the identification of oneor more ways the another transport is being operated in a differentmanner than intended; and matching the behavior pattern to one or moreof a different type of transport than the another transport and adifferent way of operating the other transport.
 2. The method of claim1, comprising: transmitting, by the server, a notification to one ormore of the another transport and a device associated with the anothertransport, in response to the consensus.
 3. The method of claim 2,wherein the notification comprises one or more of the different type ofa transport and the different way of operating the other transport. 4.The method of claim 1, wherein the identifier of the other transportcomprises one or more of a camera image and a physical description of anexterior of the other transport.
 5. The method of claim 1, wherein theone or more ways the other transport is being operated in a differentmanner than intended comprises one or more of a speed, an acceleration,towing performance, and cargo capacity of the other transport.
 6. Themethod of claim 1, comprising: creating, by each of the plurality oftransports, a blockchain transaction comprising the indications, whereineach of the plurality of transports, the other transport, and the serverare nodes or peers of a blockchain network.
 7. The method of claim 6,wherein one or more of the transports, the other transport, and theserver form the consensus by validating the blockchain transactions. 8.A transport, comprising: a processor; and a memory, coupled to theprocessor, comprising instructions that when executed by the processorare configured to: receive indications from a plurality of transports ofanother transport in proximity to the plurality of transports, eachindication comprising an identifier of the other transport and anidentification of one or more ways the other transport is being operatedin a different manner than intended; form a consensus from theindications from the plurality of transports; in response to theconsensus, determine, by the server, a behavior pattern comprising theidentification of one or more ways the another transport is operated ina different manner than intended; and match the behavior pattern to oneor more of a different type of transport than the another transport anda different way to operate the other transport.
 9. The transport ofclaim 8, further configured to: transmit, by the server, a notificationto one or more of the another transport and a device associated with theanother transport, in response to the consensus.
 10. The transport ofclaim 8, wherein the notification comprises one or more of the differenttype of transport and the different way of operating the othertransport.
 11. The transport of claim 8, wherein the identifier of theother transport comprises one or more of a camera image and a physicaldescription of an exterior of the other transport.
 12. The transport ofclaim 8, wherein the one or more ways the other transport is beingoperated in a different manner than intended comprises one or more of aspeed, an acceleration, towing performance, and cargo capacity of theother transport.
 13. The transport of claim 8, further configured to:create, by each of the plurality of transports, a blockchain transactioncomprising the indications, wherein each of the plurality of transports,the other transport, and the server are nodes or peers of a blockchainnetwork.
 14. The transport of claim 13, wherein one or more of thetransports, the other transport, and the server form the consensus byvalidating the blockchain transactions.
 15. A non-transitory computerreadable medium comprising instructions, that when read by a processor,cause the processor to perform: receiving indications from a pluralityof transports, by a server, of another transport in proximity to theplurality of transports, each indication comprising an identifier of theother transport and an identification of one or more ways the othertransports being operated in a different manner than intended; forming aconsensus, by the server, from the indications from the plurality oftransports; in response to the consensus, determining, by the server, abehavior pattern comprising the identification of one or more ways theanother transport is being operated in a different manner than intended;and matching the behavior pattern to one or more of a different type oftransport than the another transport and a different way of operatingthe other transport.
 16. The non-transitory computer readable medium ofclaim 15, wherein the instructions cause the processor to furtherperform: transmitting, by the server, a notification to one or more ofthe another transport and a device associated with the anothertransport, in response to the consensus.
 17. The non-transitory computerreadable medium of claim 16, wherein the notification comprises one ormore of the different type of transport and the different way ofoperating the other transport.
 18. The non-transitory computer readablemedium of claim 15, wherein the identifier of the other transportcomprises one or more of a camera image and a physical description of anexterior of the other transport, wherein the one or more ways the othertransport is being operated in a different manner than intendedcomprises one or more of a speed, an acceleration, towing performance,and cargo capacity of the other transport.
 19. The non-transitorycomputer readable medium of claim 15, wherein the instructions cause theprocessor to further perform: creating, by each of the plurality oftransports, a blockchain transaction comprising the indications, whereineach of the plurality of transports, the other transport, and the serverare nodes or peers of a blockchain network.
 20. The non-transitorycomputer readable medium of claim 19, wherein one or more of thetransports, the other transport, and the server form the consensus byvalidating the blockchain transactions.